Obtaining a blockchain-based, real-name, electronic bill

ABSTRACT

A computer-implemented method, non-transitory, computer-readable medium, and computer-implemented system is provided for obtaining a real-name electronic bill. In response to an association operation initiated by a user for a target electronic bill, an association transaction is published that includes an identifier of the target electronic bill, where the association transaction causes a network node on the blockchain to return identity association prompt information when determining that the target electronic bill stored in the blockchain is not associated with user identity information (UII). The UII is collected when receiving the identity association prompt information. The UII is sent to the network node, where the network node verifies whether the UII matches identity information of a payment user in the target electronic bill, and after verification succeeds, publishes an association relationship between the UII and the identifier of the target electronic bill to the blockchain for storage.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of priorityof U.S. patent application Ser. No. 16/779,511, filed Jan. 31, 2020, isa continuation of PCT Application No. PCT/CN2020/071960, filed on Jan.14, 2020, which claims priority to Chinese Patent Application No.201910703824.8, filed on Jul. 31, 2019, and each application is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

One or more implementations of the present specification relate to thefield of blockchain technologies, and in particular, to ablockchain-based real-name bill obtaining method, apparatus, and anelectronic device.

BACKGROUND

Blockchain technology, also known as distributed ledger technology, isan emerging technology in which several computing devices participate in“record-keeping” and jointly maintain a complete distributed database.Since blockchain technology has the characteristics of decentralization,openness, transparency, each computing device can participate indatabase records, and data can be quickly synchronized between computingdevices, blockchain technology has been widely used in many fields.

SUMMARY

The present specification provides a blockchain-based real-name billobtaining method, where the method is applied to a bill managementterminal interconnected with a network node on the blockchain, and theblockchain stores an electronic bill; the method includes: publishing,to the blockchain in response to an association operation initiated by auser for a target electronic bill, an association transaction thatincludes an identifier of the target electronic bill, so in response tothe association transaction, the network node on the blockchain returnsidentity association prompt information to the bill management terminalwhen determining that the target electronic bill stored in theblockchain is not associated with user identity information; collectinguser identity information when receiving the identity association promptinformation; and sending the user identity information to the networknode on the blockchain, so the network node on the blockchain verifieswhether the user identity information matches identity information of apayment user in the target electronic bill, and after verificationsucceeds, publishes an association relationship between the useridentity information and the identifier of the target electronic bill tothe blockchain for storage.

Optionally, the method further includes: publishing, to the blockchainin response to a query operation initiated by the user for the targetelectronic bill, a query transaction that includes the user identityinformation, so the network node on the blockchain searches for thetarget electronic bill associated with the user identity information inresponse to the query transaction, and returns bill information of thetarget electronic bill to the bill management terminal.

Optionally, the electronic bill stored in the blockchain is encrypted inadvance; and the method further includes: querying a decryption keycorresponding to the target electronic bill from a key managementplatform; and decrypting, based on the decryption key, the billinformation of the target electronic bill returned by the billmanagement terminal, and displaying the decrypted bill information ofthe target electronic bill to the user.

Optionally, the method further includes: invoking, in response to aprint operation initiated by the user for the target electronic bill,printing hardware loaded on the bill management terminal, and printingthe target electronic bill as a paper bill; and obtaining a bill numberof the paper bill, and publishing an association relationship betweenthe bill number of the paper bill and the identifier of the targetelectronic bill to the blockchain for storage.

Optionally, the sending the user identity information to the networknode on the blockchain, so the network node on the blockchain verifieswhether the user identity information matches identity information of apayment user in the target electronic bill includes: sending, to thenetwork node on the blockchain, a smart contract invoking transactionthat includes the user identity information, so in response to the smartcontract invoking transaction, the network node on the blockchaininvokes a verification logic declared in a smart contract deployed onthe blockchain, to verify whether the user identity information matchesthe identity information of the payment user in the target electronicbill.

The present specification further provides a blockchain-based real-namebill obtaining method, where the method is applied to a network node onthe blockchain, and the method includes: receiving an associationtransaction sent by a bill management terminal, where the associationtransaction includes an identifier of a target electronic bill; inresponse to the association transaction, sending identity associationprompt information to the bill management terminal when determining thatthe target electronic bill is not associated with user identityinformation, so the bill management terminal collects the user identityinformation; and receiving the user identity information sent by thebill management terminal, verifying whether the user identityinformation matches identity information of a payment user in the targetelectronic bill, and after verification succeeds, publishing anassociation relationship between the user identity information with theidentifier of the target electronic bill to the blockchain for storage.

Optionally, the receiving the user identity information sent by the billmanagement terminal, and verifying whether the user identity informationmatches identity information of a payment user in the target electronicbill includes: receiving a smart contract invoking transaction sent bythe bill management terminal, where the smart contract invokingtransaction includes the user identity information; and in response tothe smart contract invoking transaction, invoking a verification logicdeclared in a smart contract deployed on the blockchain to verifywhether the user identity information matches the identity informationof the payment user in the target electronic bill.

Optionally, the method further includes: receiving a query transactionsent by the bill management terminal, where the query transactionincludes the user identity information; searching for the targetelectronic bill associated with the user identity information inresponse to the query transaction; and returning bill information of thetarget electronic bill to the bill management terminal.

The present specification further provides a blockchain-based real-namebill obtaining apparatus, where the apparatus is applied to a billmanagement terminal interconnected with a network node on theblockchain, and the blockchain stores an electronic bill; the apparatusincludes: a first publishing module, configured to publish, to theblockchain in response to an association operation initiated by a userfor a target electronic bill, an association transaction that includesan identifier of the target electronic bill, so in response to theassociation transaction, the network node on the blockchain returnsidentity association prompt information to the bill management terminalwhen determining that the target electronic bill stored in theblockchain is not associated with user identity information; acollection module, configured to collect user identity information whenreceiving the identity association prompt information; and a secondpublishing module, configured to send the user identity information tothe network node on the blockchain, so the network node on theblockchain verifies whether the user identity information matchesidentity information of a payment user in the target electronic bill,and after verification succeeds, publishes an association relationshipbetween the user identity information and the identifier of the targetelectronic bill to the blockchain for storage.

Optionally, the apparatus further includes: a querying module,configured to: publish, to the blockchain in response to a queryoperation initiated by the user for the target electronic bill, a querytransaction that includes the user identity information, so the networknode on the blockchain searches for the target electronic billassociated with the user identity information in response to the querytransaction, and returns bill information of the target electronic billto the bill management terminal.

Optionally, the electronic bill stored in the blockchain is encrypted inadvance; and the apparatus further includes: a decryption module,configured to query a decryption key corresponding to the targetelectronic bill from a key management platform; and decrypt, based onthe decryption key, the bill information of the target electronic billreturned by the bill management terminal, and display the decrypted billinformation of the target electronic bill to the user.

Optionally, the apparatus further includes: a printing module,configured to: invoke, in response to a print operation initiated by theuser for the target electronic bill, printing hardware loaded on thebill management terminal, and print the target electronic bill as apaper bill; and obtain a bill number of the paper bill, and publish anassociation relationship between the bill number of the paper bill andthe identifier of the target electronic bill to the blockchain forstorage.

Optionally, the second publishing module is configured to send, to thenetwork node on the blockchain, a smart contract invoking transactionthat includes the user identity information, so in response to the smartcontract invoking transaction, the network node on the blockchaininvokes a verification logic declared in a smart contract deployed onthe blockchain, to verify whether the user identity information matchesthe identity information of the payment user in the target electronicbill.

The present specification further provides a blockchain-based real-namebill obtaining apparatus, where the apparatus is applied to a networknode on the blockchain, and the apparatus includes: a receiving module,configured to receive an association transaction sent by a billmanagement terminal, where the association transaction includes anidentifier of a target electronic bill; a returning module, configuredto: in response to the association transaction, send identityassociation prompt information to the bill management terminal whendetermining that the target electronic bill is not associated with useridentity information, so the bill management terminal collects the useridentity information; and a publishing module, configured to: receivethe user identity information sent by the bill management terminal,verify whether the user identity information matches identityinformation of a payment user in the target electronic bill, and afterverification succeeds, publish an association relationship between theuser identity information with the identifier of the target electronicbill to the blockchain for storage.

Optionally, the publishing module is configured to receive a smartcontract invoking transaction sent by the bill management terminal,where the smart contract invoking transaction includes the user identityinformation; and in response to the smart contract invoking transaction,invoke a verification logic declared in a smart contract deployed on theblockchain to verify whether the user identity information matches theidentity information of the payment user in the target electronic bill.

Optionally, the apparatus further includes: a querying module,configured to receive a query transaction sent by the bill managementterminal, where the query transaction includes the user identityinformation; searching for the target electronic bill associated withthe user identity information in response to the query transaction; andreturn bill information of the target electronic bill to the billmanagement terminal.

It can be seen from the previous description that, on one hand, the usercan associate, by using the bill management terminal, the user'selectronic bill stored in the blockchain with the user identityinformation, to implement real-name obtaining of the electronic bill.

On the other hand, after receiving the user identity information, thenetwork node on the blockchain can verify whether the user identityinformation matches the identity information of the payment user in thetarget electronic bill, thereby effectively preventing the electronicbill from being obtained by someone who does not actually own theelectronic bill.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of creating a smart contract, according toan example implementation of the present specification;

FIG. 2 is a schematic diagram of invoking a smart contract, according toan example implementation of the present specification;

FIG. 3 is a schematic diagram of creating and invoking a smart contract,according to an example implementation of the present specification;

FIG. 4 is a flowchart illustrating a blockchain-based real-name billobtaining method, according to an example implementation of the presentspecification;

FIG. 5 is a flowchart illustrating a blockchain-based real-name billobtaining method, according to an example implementation of the presentspecification;

FIG. 6 is a structural hardware diagram illustrating an electronicdevice, according to an example implementation of the presentspecification;

FIG. 7 is a block diagram illustrating a blockchain-based real-name billobtaining apparatus, according to an example implementation of thepresent specification;

FIG. 8 is a structural hardware diagram illustrating an electronicdevice, according to an example implementation of the presentspecification;

FIG. 9 is a block diagram illustrating another blockchain-basedreal-name bill obtaining apparatus, according to an exampleimplementation of the present specification.

DESCRIPTION OF IMPLEMENTATIONS

Example implementations are described in detail here, and examples ofthe example implementations are presented in the accompanying drawings.When the following description relates to the accompanying drawings,unless specified otherwise, same numbers in different accompanyingdrawings represent same or similar elements. Example implementationsdescribed in the following do not represent all implementationsconsistent with the present specification. On the contrary, theimplementations are only examples of apparatus and methods that aredescribed in the appended claims in detail and consistent with someaspects of the present specification.

It is worthwhile to note that, in other implementations, steps of acorresponding method are not necessarily performed according to asequence shown and described in the present specification. In some otherimplementations, the method can include more or less steps than thosedescribed in the present specification. In addition, a single stepdescribed in the present specification can be broken down into multiplesteps in other implementations for description. However, the multiplesteps described in the present specification can also be combined into asingle step for description in other implementations.

A blockchain is generally classified into three types: a publicblockchain, a private blockchain, and a consortium blockchain. Inaddition, there are several types of combinations, such as privateblockchain+consortium blockchain and consortium blockchain+publicblockchain.

The public blockchain has the highest degree of de-centralization. Thepublic blockchain is represented by Bitcoin and Ethereum. Participants(also referred to as blockchain nodes) who join the public blockchaincan read on-chain data records, participate in transactions, and competefor accounting rights of new blocks. In addition, each node can freelyjoin or exit a network and perform related operations.

On the contrary, a write right of the private blockchain network iscontrolled by a certain organization or institution, and a data readingright is specified by the organization. In short, the private blockchaincan be a weak centralization system, and participating nodes arestrictly limited and rare. This type of blockchain is more suitable forinternal use within a specific organization.

The consortium blockchain is a blockchain balanced between the publicblockchain and the private blockchain, and can be “partiallydecentralized”. Each node in the consortium blockchain usually has acorresponding entity institution or organization. Nodes join the networkthrough authorization and form interest-related consortiums to jointlymaintain blockchain operation.

Based on the basic characteristics of the blockchain, the blockchainusually consists of several blocks. Timestamps corresponding to creationmoments of these blocks are separately recorded in these blocks, and allthe blocks strictly form a time-ordered data chain based on thetimestamps recorded in the blocks.

For real data generated in the physical world, the data can be formedinto a standard transaction format supported by the blockchain, and thenpublished to the blockchain. Network nodes in the blockchain performconsensus processing on the received transaction. After the consensus isreached, a network node serving as a bookkeeping node in the blockchainseals the transaction into a block and persistently stores thetransaction in the blockchain.

Consensus algorithms supported in the blockchain can include: afirst-type consensus algorithm where a network node needs to compete forthe bookkeeping right in each round of bookkeeping, such as Proof ofWork (POW), Proof of Stake (POS), and Delegated Proof of Stake (DPOS); asecond-type consensus algorithm where a bookkeeping node is elected inadvance for each round of bookkeeping (there is no need to compete forthe bookkeeping right), such as a Practical Byzantine Fault Tolerance(PBFT).

In a blockchain network using the first-type consensus algorithm, allnetwork nodes that compete for the bookkeeping right can execute atransaction after receiving the transaction. One of the network nodesthat compete for the bookkeeping right can prevail in a current roundand become the bookkeeping node. The bookkeeping node can seal areceived transaction with other transactions to generate a latest block,and send the generated latest block or a block header of the latestblock to other network nodes for reaching consensus.

In a blockchain network using the second-type consensus algorithm, anetwork node having the bookkeeping right has been agreed upon beforethe current round of bookkeeping. Therefore, after receiving atransaction, a network node can send the transaction to the bookkeepingnode if the network node is not the bookkeeping node of the currentround. The bookkeeping node in the current round can execute thetransaction when or before sealing the transaction with othertransactions to generate a latest block. After generating the latestblock, the bookkeeping node can send the latest block or a block headerof the latest block to other network nodes for reaching consensus.

As described above, regardless of which consensus algorithm is used inthe blockchain, the bookkeeping node in the current round can seal thereceived transaction to generate the latest block, and send thegenerated latest block or the block header of the latest block to othernetwork nodes for consensus verification. After receiving the latestblock or the block header of the latest block, if the other networknodes verify that the latest block is correct, the other network nodescan append the latest block to the end of the original blockchain, so asto complete a bookkeeping process of the blockchain. In the process ofverifying a new block or block header from the bookkeeping node, theother nodes can also execute a transaction included in the block.

In addition, in practice, the smart contract function can be providedfor public, private, and consortium blockchains. The smart contract onthe blockchain is a contract that can be triggered by a transaction onthe blockchain. The smart contract is defined in the form of codes.

Taking Ethereum as an example, users can create and invoke some complexlogics in the Ethereum network. An Ethereum virtual machine (EVM) is thecore of Ethereum, which is a programmable blockchain, and each Ethereumnode can run the EVM. The EVM is a Turing-complete virtual machine,through which various complex logics can be implemented. The userpublishes and invokes the smart contract actually on the EVM in theEthereum. In fact, the EVM directly runs virtual machine codes (virtualmachine bytecode, “bytecode” for short), so the smart contract deployedon the blockchain can be bytecodes.

As shown in FIG. 1, after Bob sends a transaction containing informationabout creating a smart contract to the Ethereum network, each node canexecute the transaction in the EVM. The From field of the transaction inFIG. 1 is used to record an address of an account that initiates thecreating of the smart contract. Contract codes stored in a field valueof the Data field of the transaction can be bytecodes, and a field valueof the To field of the transaction is a null account. After a consensusis reached between nodes based on a consensus mechanism, the smartcontract is successfully created. Subsequently, a user can invoke thesmart contract.

After a smart contract is created, a contract account corresponding tothe smart contract appears on the blockchain and has a specific address.For example, “0x68e12cf284 . . . ” on each node in FIG. 1 represents theaddress of the created contract account. A contract code and accountstorage are stored in the account storage of the contract account. Thebehavior of the smart contract is controlled by the contract code, andthe account storage of the smart contract keeps the contract status. Inother words, the smart contract causes a virtual account including thecontract codes and account storage to be generated on the blockchain.

As mentioned above, the Data field of the transaction containinginformation about creating a smart contract can store the bytecodes ofthe smart contract. The bytecode consists of a series of bytes. Eachbyte can identify one operation. Based on development efficiency,readability, etc., developers could not write bytecodes directly, butchoose high-level languages to write smart contract codes. For example,the high-level languages can be Solidity, Serpent, LLL, etc. For smartcontract codes compiled in high-level languages, bytecodes that can bedeployed on the blockchain can be generated through compiling by acompiler.

The Solidity language is used as an example. Contract codes compiled byusing the Solidity language are similar to the Class in anobject-oriented programming language. Multiple members can be declaredin a contract, including a status variable, a function, a functionmodifier, an event, etc. The status variable is a value that ispermanently stored in the account storage field of the smart contractand is used to store the status of the contract.

As shown in FIG. 2, Ethereum is still used as an example. After Bobsends a transaction containing information about invoking a smartcontract to the Ethereum network, each node can execute the transactionin the EVM. In FIG. 2, the From field of the transaction is used torecord an address of an account that initiates the invoking of the smartcontract, the To field is used to record an address of the invoked smartcontract, and the Data field of the transaction is used to record amethod and a parameter for invoking the smart contract. After the smartcontract is invoked, the account status of the contract account canchange. Subsequently, a certain client can view the account status ofthe contract account by using an accessed blockchain node (for example,node 1 in FIG. 2).

The smart contract can be executed independently on each node in theblockchain network in a specified method, and all execution records anddata are stored in the blockchain. Therefore, after such a transactionis executed, transaction vouchers that cannot be tampered with and willnot be lost are stored in the blockchain.

A schematic diagram of creating a smart contract and invoking a smartcontract is shown in FIG. 3. Creating a smart contract in Ethereumrequires the following processes: compiling the smart contract, changingthe smart contract into bytecodes, and deploying the bytecodes to theblockchain. Invoking a smart contract in Ethereum means initiating atransaction pointing to a smart contract address. An EVM of each nodecan separately execute the transaction, and smart contract codes aredistributed on a virtual machine of each node in the Ethereum network.

In addition, in an inter-blockchain scenario, multiple blockchains canbe interconnected by using inter-blockchain relays.

The inter-blockchain relay can separately interconnect with multipleblockchains by using bridging interfaces, and implement inter-blockchaindata synchronization between the multiple blockchains based on animplemented data transport logic.

An inter-blockchain technology used to implement the previousinter-blockchain relay is not specifically limited in the presentspecification. For example, in practice, multiple blockchains can beconnected by using an inter-blockchain mechanism such as a sidechaintechnology or a notary technology.

After multiple blockchains are interconnected by using inter-blockchainrelays, data on other blockchains can be read and authenticated betweenthe blockchains, or smart contracts deployed on other blockchains can beinvoked by using inter-blockchain relays.

In addition to using data stored in the blockchain, the smart contractdeployed on the blockchain can also use the Oracle machine to referencedata on a data entity off the chain, so as to implement data exchangebetween the smart contract and the real-world data entity. The off-chaindata entity can include a centralized server or data center deployed offthe chain, etc.

Different from inter-blockchain relays, the Oracle machine does notsynchronize data on one blockchain to another blockchain, butsynchronizes data on an off-chain data entity to the blockchain.

That is, the inter-blockchain relay is used to connect two blockchains,and the Oracle machine is used to connect a blockchain with an off-chaindata entity to implement data exchange between the blockchain and thereal world.

As service scenarios of the blockchain become increasingly rich, inaddition to services related to value transfer, such as transfer, moreand more blockchain projects begin to introduce traditional servicescenarios that are not related to value transfer. For example, a servicesystem can be interconnected with a service blockchain to implementtraditional service scenarios such as issuance and reimbursement ofelectronic bills on the service blockchain.

In the existing field of electronic bill querying, a user usuallyqueries an electronic bill based on an identifier of the electronic bill(such as a code and a number of the electronic bill). However, on onehand, the identifier of the electronic bill has lots of numbers, whichare not easy for the user to record. On the other hand, the user needsto enter the identifier of each electronic bill to find the electronicbill. Therefore, using the identifier of the electronic bill to querythe electronic bill brings inconvenience to the user, and reduces theefficiency of querying the electronic bill.

The present specification is intended to provide a blockchain-basedreal-name bill obtaining method. An association relationship betweenuser identity information and an electronic bill of a user is stored ina blockchain, so the user can subsequently find an electronic bill ownedby the user by using the user identity information.

During implementation, a bill management terminal publishes, to theblockchain in response to an association operation initiated by a userfor a target electronic bill, an association transaction that includesan identifier of the target electronic bill. In response to theassociation transaction, a network node on the blockchain returnsidentity association prompt information to the bill management terminalwhen determining that the target electronic bill stored in theblockchain is not associated with user identity information.

The bill management terminal collects user identity information whenreceiving the identity association prompt information; and sends theuser identity information to the network node on the blockchain, so thenetwork node on the blockchain verifies whether the user identityinformation matches identity information of a payment user in the targetelectronic bill, and after verification succeeds, publishes anassociation relationship between the user identity information and theidentifier of the target electronic bill to the blockchain for storage.

It can be seen from the previous description that, the user canassociate, by using the bill management terminal, the user's electronicbill stored in the blockchain with the user identity information, toimplement real-name obtaining of the electronic bill.

In addition, in a subsequent electronic bill querying process, the usercan query the user's electronic bill from the blockchain based on theuser identity information, which facilitates querying of the electronicbill.

Referring to FIG. 4, FIG. 4 is a flowchart illustrating ablockchain-based real-name bill obtaining method, according to anexample implementation of the present specification. The method can beapplied to a bill management terminal, and can include the followingsteps.

Step 402: Publish, to the blockchain in response to an associationoperation initiated by a user for a target electronic bill, anassociation transaction that includes an identifier of the targetelectronic bill, so in response to the association transaction, anetwork node on the blockchain returns identity association promptinformation to the bill management terminal when determining that thetarget electronic bill stored in the blockchain is not associated withuser identity information.

Step 404: Collect user identity information when receiving the identityassociation prompt information.

Step 406: Send the user identity information to the network node on theblockchain, so the network node on the blockchain verifies whether theuser identity information matches identity information of a payment userin the target electronic bill, and after verification succeeds,publishes an association relationship between the user identityinformation and the identifier of the target electronic bill to theblockchain for storage.

Referring to FIG. 5, FIG. 5 is a flowchart illustrating ablockchain-based real-name bill obtaining method, according to anexample implementation of the present specification. The method can beapplied to a network node on the blockchain, and can include thefollowing steps.

Step 502: Receive an association transaction sent by a bill managementterminal, where the association transaction includes an identifier of atarget electronic bill.

Step 504: In response to the association transaction, send identityassociation prompt information to the bill management terminal whendetermining that the target electronic bill is not associated with useridentity information, so the bill management terminal collects the useridentity information.

Step 506: Receive the user identity information sent by the billmanagement terminal, verify whether the user identity informationmatches identity information of a payment user in the target electronicbill, and after verification succeeds, publish an associationrelationship between the user identity information with the identifierof the target electronic bill to the blockchain for storage.

The previous bill management terminal refers to a terminal device thathas a bill management function. The user can use the bill managementterminal to obtain electronic bills using the real name, queryelectronic bills, and print electronic bills.

For example, in the medical field, the bill management terminal can be amanagement device that is deployed by a medical institution and that hasa medical invoice management function. The bill management terminal andits functions are merely described here by way of example, and are notspecifically limited.

The above electronic bill identifier refers to information that uniquelyidentifies an electronic bill.

For example, when the previous electronic bill is an invoice, theelectronic bill identifier can be an invoice code, an invoice number, ora combination of an invoice code and an invoice number.

The previous user information can include a name of the user, anidentity card number of the user, physiological characteristicinformation of the user, etc. The physiological characteristicinformation of the user can include: face characteristic information ofthe user, fingerprint characteristic information of the user, irischaracteristic information of the user, etc. The user information andthe physiological characteristic information of the user are merelydescribed here by way of example, and are not specifically limited.

In addition, the blockchain disclosed in this description can be one ora combination of a public blockchain, a private blockchain, and aconsortium blockchain. The blockchain disclosed in this description ismerely described by way of example, and is not specifically limited.Electronic bills are stored in the blockchain disclosed in the presentspecification.

The following describes in detail the blockchain-based real-name billobtaining method from real-name obtaining of the electronic bill andquerying of the electronic bill.

1) Real-Name Obtaining of Electronic Bill

A user can initiate an association operation for a target electronicbill by using a bill management terminal.

For example, the interface of the bill management terminal is deployedwith an “association option” and a bill identifier entry bar of anelectronic bill that the user needs to associate with. The user canenter the identifier of the target electronic bill in the entry bar, andthen trigger the “association option”. As such, the user can initiate anassociation operation for the target electronic bill by using the billmanagement terminal.

Certainly, “the user can initiate an association operation for thetarget electronic bill by using the bill management terminal” is merelydescribed here by way of example and is not specifically limited.

When detecting the association operation performed by the user for thetarget electronic bill, the bill management terminal can publish, to anetwork node on the blockchain in response to the association operationinitiated by the user for the target electronic bill, an associationtransaction that includes the identifier of the target electronic bill.The association transaction includes the identifier of the targetelectronic bill.

When receiving the association transaction, the network node on theblockchain can search for the target electronic bill in response to theassociation transaction based on the identifier of the target electronicbill included in the association transaction. Then, the network node onthe blockchain can further detect whether the found target electronicbill is associated with user identity information.

If the target electronic bill is associated with user identityinformation, the network node on the blockchain returns promptinformation indicating that the target electronic bill is associatedwith user identity information to the bill management terminal, so thebill management terminal displays the prompt information indicating thatthe target electronic bill is associated with user identity informationto the user.

If the target electronic bill is not associated with user identityinformation, the network node on the blockchain returns identityassociation prompt information to the bill management terminal.

When receiving the identity association prompt information returned bythe network node on the blockchain, the bill management terminal cancollect the user identity information. For example, the bill managementterminal can collect an identity card number of the user, facial featureinformation, fingerprint information, voiceprint information, and irisinformation of the user.

For example, during collection, the bill management terminal candisplay, on the interface of the terminal, prompt information used toprompt the user to enter identity information. After seeing the promptinformation, the user can enter the identity number of the user on thebill management terminal. The bill management terminal can obtain theidentity number entered by the user, so as to collect the identityinformation of the user. Certainly, the bill management terminal canfurther invoke identity card scanning hardware deployed in the terminalto obtain the identity card number of the user by scanning the identitycard of the user.

For another example, the bill management terminal can further invokeimage collection hardware (such as a camera) deployed on the terminal tocollect a face image of the user, and extract face feature informationof the user.

For another example, the bill management terminal can further invokeaudio collection hardware (such as a microphone) deployed on theterminal to collect sound information of the user. The bill managementterminal can further invoke fingerprint collection hardware to collectfingerprint information of the user. The bill management terminal canfurther invoke iris collection hardware to collect iris information ofthe user, etc. his is merely described by way of example, and is notspecifically limited.

In the implementation of the present specification, after collecting theuser identity information, the bill management terminal can send theuser identity information to the network node on the blockchain.

To prevent the electronic bill from being obtained by someone who doesnot actually own the electronic bill, after receiving the user identityinformation, the network node on the blockchain can check whether theuser identity information matches identity information of a payment userin the target electronic bill.

In an optional method, the network node on the blockchain can locallycheck whether the user identity information matches the identityinformation of the payer in the target electronic bill.

In another optional method, a smart contract is deployed on theblockchain, and the smart contract includes a verification logic. Theverification logic is used to verify whether the user identityinformation matches the identity information of the payment user in thetarget electronic bill. The method for creating the smart contract canbe shown in FIG. 1, and details are omitted here for simplicity.

In actual application, the bill management terminal can send, to thenetwork node on the blockchain, a smart contract invoking transactionthat includes the user identity information. In response to the smartcontract invoking transaction, the network node on the blockchain caninvoke the verification logic declared in the smart contract deployed onthe blockchain to verify whether the user identity information matchesthe identity information of the payment user in the target electronicbill.

For example, the identity information of the payment user in theelectronic bill usually includes the payer name etc.

The collected user information usually includes a unique identity of theuser, for example, the identity card number of the user and thephysiological characteristic information of the user.

“Verify whether the user identity information matches the identityinformation of the payment user in the target electronic bill” isdescribed by using an example that the collected user information is theidentity card number of the user and the payer identity information ofthe electronic bill is the payer name.

When verifying whether the user identity information matches theidentity information of the payment user in the target electronic bill,the network node on the blockchain can first obtain a user nameassociated with the identity card number of the user, and then verifywhether the user name associated with the identity card number of theuser matches the name of the payer in the electronic bill.

The user name associated with the identity card number of the user canbe obtained in the following methods.

Method 1: The previous blockchain stores a correspondence betweenidentity card numbers of users and user names.

The network node on the blockchain can search the correspondence, storedin the blockchain, between identity card numbers of users and user namesfor a user name corresponding to a collected identity card number of auser.

Method 2: An off-chain server stores a correspondence between identitycard numbers of users and user names.

The network node on the blockchain can obtain, by using the Oraclemachine, the user name corresponding to the collected identity cardnumber of the user from the off-chain server.

Certainly, in the present specification, another blockchain other thanthe previous blockchain can be separately deployed, and a correspondencebetween identity card numbers of users and user names is stored in theanother blockchain.

The network node on the blockchain can obtain, by using aninter-blockchain relay, the user name corresponding to the collectedidentity card number of the user from the another blockchain.

Obtaining the user name associated with the identity card number of theuser is described by way of example, and is not specifically limited.

In the present specification, when the network node on the blockchaindetermines that the collected user identity information matches theidentity information of the payment user in the target electronic bill,the network node on the blockchain can publish an associationrelationship between the collected user identity information and theidentifier of the target electronic bill to the blockchain for storage.

It can be seen from the previous description that, on one hand, the usercan associate, by using the bill management terminal, the user'selectronic bill stored in the blockchain with the user identityinformation, to implement real-name obtaining of the electronic bill.

On the other hand, after receiving the user identity information, thenetwork node on the blockchain can verify whether the user identityinformation matches the identity information of the payment user in thetarget electronic bill, thereby effectively preventing the electronicbill from being obtained by someone who does not actually own theelectronic bill.

2) Querying of Electronic Bill

After an electronic bill is obtained by using a real name, anassociation relationship between an identifier of the electronic billand user identity information is stored in a blockchain.

A user can query the user's own electronic bill based on user identityinformation.

During implementation, the user can initiate a query operation for atarget electronic bill by using a bill management terminal.

For example, the user can enter the user identity information on a queryinterface of the bill management terminal, so as to initiate a queryoperation for the target electronic bill.

After detecting the query operation performed by the user for the targetelectronic bill, the bill management terminal can publish a querytransaction to the blockchain. The query transaction includes the useridentity information.

In response to the query transaction, the network node on the blockchaincan search a correspondence, stored in the blockchain, between useridentity information and electronic bill identifiers, the identifier ofthe target electronic bill corresponding to the user identityinformation included in the query transaction. Ten, the network node onthe blockchain returns bill information of the target electronic billindicated by the electronic bill identifier to the bill managementterminal.

In addition, to ensure the security of the user's electronic bill, theelectronic bill stored in the blockchain is usually encrypted.

A decryption key of the electronic bill can be stored on a keymanagement platform interconnected with the bill management device.

The bill management terminal can obtain the decryption key correspondingto the target electronic bill from the key management platform, thendecrypt, by using the decryption key, the bill information of the targetelectronic bill returned by the network node on the blockchain, anddisplay the decrypted bill information of the target electronic bill tothe user.

It can be seen from the previous description that, instead of queryingeach electronic bill owned by the user by using an identifier of theelectronic bill, the user can query all electronic bills owned by theuser by using the user identity information, thereby effectivelyimproving efficiency of querying the electronic bills owned by the user.

In addition, in the implementation of the present specification, theuser can print the queried target electronic bill by using the billmanagement terminal.

To prevent the user from performing multiple repeated reimbursements byusing the paper bill and the electronic bill, the bill managementterminal can further publish an association relationship between a billnumber of the paper bill printed by the user and the identifier of thetarget electronic bill to the blockchain for storage.

During specific implementation, the user can initiate a print operationfor the target electronic bill by using the bill management terminal.

For example, the bill management terminal has a “print” option on theinterface for displaying the bill information of the target electronicbill to the user. The user can click the “print” option to initiate aprint operation for the target electronic bill.

In response to the print operation initiated by the user for the targetelectronic bill, the bill management terminal can invoke print hardwareloaded on the bill management terminal to print the target electronicbill as a paper bill.

Then, the bill management terminal can obtain the bill number of thepaper bill. During obtaining, the bill management terminal can invokescanning hardware loaded on the bill management terminal to scan thepaper bill to obtain the bill number of the paper bill. Certainly, theuser can further enter the bill number of the paper bill on the billmanagement terminal, and the bill management terminal can obtain thebill number of the paper bill that is entered by the user.

After obtaining the bill number of the paper bill, the bill managementterminal can publish an association relationship between the bill numberof the paper bill and the identifier of the target electronic bill tothe blockchain for storage.

It can be seen from the previous description that, on one hand, the usercan associate, by using the bill management terminal, the user'selectronic bill stored in the blockchain with the user identityinformation, to implement real-name obtaining of the electronic bill.

On the other hand, after receiving the user identity information, thenetwork node on the blockchain can verify whether the user identityinformation matches the identity information of the payment user in thetarget electronic bill, thereby effectively preventing the electronicbill from being obtained by someone who does not actually own theelectronic bill.

Furthermore, after the user prints the queried target electronic billinto a paper bill, the bill number of the paper bill and the identifierof the target electronic bill can be published to the blockchain forstorage, so as to prevent the user from performing multiple repeatedreimbursements.

Corresponding to the previous method implementation of FIG. 4, thepresent specification further provides an implementation of ablockchain-based real-name bill obtaining apparatus. The implementationof the blockchain-based real-name bill obtaining apparatus in thepresent specification can be applied to an electronic device. Theapparatus implementation can be implemented by software, hardware, or acombination of hardware and software. Software implementation is used asan example. As a logical device, the device is formed by reading acorresponding computer program instruction in a non-volatile memory to amemory by a processor of an electronic device where the device islocated. In terms of hardware, referring to FIG. 6, FIG. 6 is astructural hardware diagram illustrating an electronic device that theblockchain-based real-name bill obtaining apparatus is located in thepresent specification. In addition to a processor, a memory, a networkinterface, and a non-volatile memory shown in FIG. 6, the electronicdevice that the apparatus is located in the implementations can usuallyinclude other hardware based on an actual function of the electronicdevice. Details are omitted here for simplicity.

Referring to FIG. 7, FIG. 7 is a block diagram illustrating ablockchain-based real-name bill obtaining apparatus, according to anexample implementation of the present specification. The apparatus isapplied to a bill management terminal interconnected with a network nodeon the blockchain, and the blockchain stores an electronic bill; theapparatus includes: a first publishing module 701, configured topublish, to the blockchain in response to an association operationinitiated by a user for a target electronic bill, an associationtransaction that includes an identifier of the target electronic bill,so in response to the association transaction, the network node on theblockchain returns identity association prompt information to the billmanagement terminal when determining that the target electronic billstored in the blockchain is not associated with user identityinformation; a collection module 702, configured to collect useridentity information when receiving the identity association promptinformation; and a second publishing module 703, configured to send theuser identity information to the network node on the blockchain, so thenetwork node on the blockchain verifies whether the user identityinformation matches identity information of a payment user in the targetelectronic bill, and after verification succeeds, publishes anassociation relationship between the user identity information and theidentifier of the target electronic bill to the blockchain for storage.

Optionally, the apparatus further includes: a querying module 704 (notshown in FIG. 7), configured to: publish, to the blockchain in responseto a query operation initiated by the user for the target electronicbill, a query transaction that includes the user identity information,so the network node on the blockchain searches for the target electronicbill associated with the user identity information in response to thequery transaction, and returns bill information of the target electronicbill to the bill management terminal.

Optionally, the electronic bill stored in the blockchain is encrypted inadvance; and the apparatus further includes: a decryption module 705(not shown in FIG. 7), configured to query a decryption keycorresponding to the target electronic bill from a key managementplatform; and decrypt, based on the decryption key, the bill informationof the target electronic bill returned by the bill management terminal,and display the decrypted bill information of the target electronic billto the user.

Optionally, the apparatus further includes: a printing module 706 (notshown in FIG. 7), configured to: invoke, in response to a printoperation initiated by the user for the target electronic bill, printinghardware loaded on the bill management terminal, and print the targetelectronic bill as a paper bill; and obtain a bill number of the paperbill, and publish an association relationship between the bill number ofthe paper bill and the identifier of the target electronic bill to theblockchain for storage.

Optionally, the second publishing module 703 is configured to send, tothe network node on the blockchain, a smart contract invokingtransaction that includes the user identity information, so in responseto the smart contract invoking transaction, the network node on theblockchain invokes a verification logic declared in a smart contractdeployed on the blockchain, to verify whether the user identityinformation matches the identity information of the payment user in thetarget electronic bill.

Corresponding to the previous method implementation of FIG. 5, thepresent specification further provides an implementation of ablockchain-based real-name bill obtaining apparatus. The implementationof the blockchain-based real-name bill obtaining apparatus in thepresent specification can be applied to an electronic device. Theapparatus implementation can be implemented by software, hardware, or acombination of hardware and software. Software implementation is used asan example. As a logical device, the device is formed by reading acorresponding computer program instruction in a non-volatile memory to amemory by a processor of an electronic device where the device islocated. In terms of hardware, referring to FIG. 8, FIG. 8 is astructural hardware diagram illustrating an electronic device that theblockchain-based real-name bill obtaining apparatus is located in thepresent specification. In addition to a processor, a memory, a networkinterface, and a non-volatile memory shown in FIG. 8, the electronicdevice that the apparatus is located in the implementations can usuallyinclude other hardware based on an actual function of the electronicdevice. Details are omitted here for simplicity.

Referring to FIG. 9, FIG. 9 is a block diagram illustrating anotherblockchain-based real-name bill obtaining apparatus, according to anexample implementation of the present specification. The apparatus isapplied to a network node on the blockchain, and the apparatus includes:a receiving module 901, configured to receive an association transactionsent by a bill management terminal, where the association transactionincludes an identifier of a target electronic bill; a returning module902, configured to: in response to the association transaction, sendidentity association prompt information to the bill management terminalwhen determining that the target electronic bill is not associated withuser identity information, so the bill management terminal collects theuser identity information; and a publishing module 903, configured to:receive the user identity information sent by the bill managementterminal, verify whether the user identity information matches identityinformation of a payment user in the target electronic bill, and afterverification succeeds, publish an association relationship between theuser identity information with the identifier of the target electronicbill to the blockchain for storage.

Optionally, the publishing module 903 is configured to receive a smartcontract invoking transaction sent by the bill management terminal,where the smart contract invoking transaction includes the user identityinformation; and in response to the smart contract invoking transaction,invoke a verification logic declared in a smart contract deployed on theblockchain to verify whether the user identity information matches theidentity information of the payment user in the target electronic bill.

Optionally, the apparatus further includes: a querying module 904 (notshown in FIG. 9), configured to receive a query transaction sent by thebill management terminal, where the query transaction includes the useridentity information; searching for the target electronic billassociated with the user identity information in response to the querytransaction; and return bill information of the target electronic billto the bill management terminal.

The system, apparatus, module, or unit illustrated in the previousimplementations can be implemented by using a computer chip or anentity, or can be implemented by using a product having a certainfunction. A typical implementation device is a computer, and thecomputer can be a personal computer, a laptop computer, a cellularphone, a camera phone, a smartphone, a personal digital assistant, amedia player, a navigation device, an email receiving and sendingdevice, a game console, a tablet computer, a wearable device, or anycombination of these devices.

In a typical configuration, the computer includes one or more processors(CPU), input/output interfaces, network interfaces, and memories.

The memory can include a non-persistent memory, a random access memory(RAM), a non-volatile memory, and/or another form that are in a computerreadable medium, for example, a read-only memory (ROM) or a flash memory(flash RAM). The memory is an example of the computer readable medium.

The computer readable medium includes persistent, non-persistent,movable, and unmovable media that can store information by using anymethod or technology. The information can be a computer readableinstruction, a data structure, a program module, or other data. Examplesof a computer storage medium include but are not limited to a phasechange random access memory (PRAM), a static RAM (SRAM), a dynamic RAM(DRAM), a RAM of another type, a read-only memory (ROM), an electricallyerasable programmable ROM (EEPROM), a flash memory or another memorytechnology, a compact disc ROM (CD-ROM), a digital versatile disc (DVD)or another optical storage, a cassette tape, a magnetic disk storage, aquantum memory, a storage medium based on grapheme, another magneticstorage device, or any other non-transmission medium. The computerstorage medium can be used to store information that can be accessed bythe computing device. Based on the definition in the presentspecification, the computer readable medium does not include transitorycomputer readable media (transitory media) such as a modulated datasignal and carrier.

It is worthwhile to further note that, the terms “include”, “contain”,or their any other variants are intended to cover a non-exclusiveinclusion, so a process, a method, a product or a device that includes alist of elements not only includes those elements but also includesother elements which are not expressly listed, or further includeselements inherent to such process, method, product or device. Withoutmore constraints, an element preceded by “includes a . . . ” does notpreclude the existence of additional identical elements in the process,method, product or device that includes the element.

Specific implementations of the present specification are describedabove. Other implementations fall within the scope of the appendedclaims. In some situations, the actions or steps described in the claimscan be performed in an order different from the order in theimplementations and the desired results can still be achieved. Inaddition, the process depicted in the accompanying drawings does notnecessarily need a particular execution order to achieve the desiredresults. In some implementations, multi-tasking and concurrentprocessing is feasible or can be advantageous.

Terms used in one or more implementations of the present specificationare merely used to describe specific implementations, and are notintended to limit the one or more implementations of the presentspecification. The terms “a” and “the” of singular forms used in one ormore implementations of the present specification and the appendedclaims are also intended to include plural forms, unless otherwisespecified in the context clearly. It should be further understood thatthe term “and/or” used in the present specification indicates andincludes any or all possible combinations of one or more associatedlisted items.

It should be understood that although terms “first”, “second”, “third”,etc. can be used in one or more implementations of the presentspecification to describe various types of information, the informationis not limited to these terms. These terms are only used todifferentiate between information of the same type. For example, withoutdeparting from the scope of one or more implementations of the presentspecification, first information can also be referred to as secondinformation, and similarly, the second information can be referred to asthe first information. Depending on the context, for example, the word“if” used here can be explained as “while”, “when”, or “in response todetermining”.

The previous descriptions are only example implementations of one ormore implementations of the present specification, but are not intendedto limit the one or more implementations of the present specification.Any modification, equivalent replacement, improvement, etc. made withoutdeparting from the spirit and principle of the one or moreimplementations of the present specification shall fall within theprotection scope of the one or more implementations of the presentspecification.

What is claimed is:
 1. A computer-implemented method for obtaining areal-name electronic bill, comprising: storing, by a network node on ablockchain, a target electronic bill, wherein the target electronic billcomprises an identifier of the target electronic bill and identityinformation of a payment user in the target electronic bill; receiving,by a bill management terminal, a first input of a user, wherein thefirst input of the user comprises a first request to associate the userwith the target electronic bill and the identifier of the targetelectronic bill; sending, by the bill management terminal and to thenetwork node on the blockchain, a second request to associate the userwith the target electronic bill stored in the blockchain, wherein thesecond request comprises the identifier of the target electronic bill;receiving, by the network node on the blockchain, the second request; inresponse to receiving the second request, searching, by the network nodeon the blockchain, for the target electronic bill in the blockchainbased on the identifier of the target electronic bill comprised in thesecond request; determining, by the network node on the blockchain, thatthe target electronic bill stored in the blockchain is not associatedwith user identity information of the user; in response to determiningthat the target electronic bill stored in the blockchain is notassociated with the user identity information of the user, sending, bythe network node on the blockchain and to the bill management terminal,a third request for user information; in response to receiving the thirdrequest for user information, collecting, by the bill managementterminal, the user identity information of the user from user identityinformation collecting hardware, wherein collecting the user identityinformation of the user comprises: activating, by the bill managementterminal, the user identity information collecting hardware; andobtaining, by the bill management terminal, the user identityinformation of the user by using the user identity informationcollecting hardware; sending, by the bill management terminal, the useridentity information of the user to the network node on the blockchain;receiving, by the network node on the blockchain and from the billmanagement terminal, the user identity information of the user;verifying, by the network node on the blockchain, whether the useridentity information of the user matches the identity information of thepayment user in the target electronic bill; determining, by the networknode on the blockchain, that the user identity information of the usermatches the identity information of the payment user in the targetelectronic bill; in response to determining that the user identityinformation of the user matches the identity information of the paymentuser in the target electronic bill, publishing, by the network node onthe blockchain, the matched determination on the blockchain; receiving,by the bill management terminal, a second input of the user, the secondinput of the user comprising a print operation to print the targetelectronic bill; activating, by the bill management terminal, printhardware coupled with the bill management terminal; and printing, by thebill management terminal, a paper bill corresponding to the targetelectronic bill using the print hardware.
 2. The computer-implementedmethod of claim 1, further comprising: storing, by the network node onthe blockchain, a correspondence between the user identity informationof the user and one or more electronic bill identifiers; receiving, bythe bill management terminal, a third input of the user, wherein thethird input of the user comprises a fourth request and the user identityinformation of the user; sending, by the bill management terminal and tothe network node on the blockchain, a fifth request, wherein the fifthrequest comprises the user identity information of the user; receiving,by the network node on the blockchain, the fifth request; and inresponse to the fifth request, searching, by the network node on theblockchain, the correspondence stored in the blockchain between the useridentity information of the user and the one or more electronic billidentifiers.
 3. The computer-implemented method of claim 2, furthercomprising: determining, by the network node on the blockchain, that theone or more electronic bill identifiers comprise the identifier of thetarget electronic bill corresponding to the user identity information ofthe user included in the fifth request; and sending, by the network nodeon the blockchain and to the bill management terminal, bill informationof the target electronic bill.
 4. The computer-implemented method ofclaim 3, further comprising: receiving, by the bill management terminalfrom the network node on the blockchain, the bill information of thetarget electronic bill, wherein the bill information of the targetelectronic bill is encrypted; querying, by the bill management terminalfrom a key management platform, a decryption key corresponding to thetarget electronic bill; decrypting, by the bill management terminal, thebill information of the target electronic bill using the decryption key;and displaying, by the bill management terminal, the decrypted billinformation of the target electronic bill.
 5. The computer-implementedmethod of claim 1, wherein the verifying, by the network node on theblockchain, whether the user identity information of the user matchesidentity information of a payment user in the target electronic billcomprises: invoking, by the network node on the blockchain, a smartcontract; and verifying, by the network node on the blockchain via thesmart contract, whether the user identity information of the usermatches the identity information of the payment user in the targetelectronic bill.
 6. The computer-implemented method of claim 1, whereinthe user identity information of the user is collected by the billmanagement terminal in response to displaying, by the bill managementterminal, a prompt for the user identity information.
 7. Thecomputer-implemented method of claim 1, wherein: the user identityinformation of the user comprises a unique identifier of the user, theidentity information of the payment user in the target electronic billcomprises a name of a payer of the target electronic bill, and theverifying, by the network node on the blockchain, whether the useridentity information of the user matches identity information of apayment user in the target electronic bill comprises: obtaining, by thenetwork node on the blockchain via an oracle machine or aninter-blockchain relay, a name of the user corresponding to the uniqueidentifier of the user from an off-chain server; and verifying whetherthe name of the user matches the name of the payer of the targetelectronic bill.
 8. The computer-implemented method of claim 1, wherein:the user identity information of the user comprises an identity cardnumber of the user, and the user identity information collectinghardware comprises identity card scanning hardware, and the obtaining,by the bill management terminal, the user identity information of theuser by using the user identity information collecting hardwarecomprises obtaining, by the bill management terminal, the identity cardnumber of the user by scanning an identity card of the user using theidentity card scanning hardware.
 9. The computer-implemented method ofclaim 1, wherein: the user identity information of the user comprisesone or more of physiological characteristic information of the user, theuser identity information collecting hardware comprises image collectionhardware, and the obtaining, by the bill management terminal, the useridentity information of the user by using the user identity informationcollecting hardware comprises obtaining, by the bill managementterminal, a face image of the user using the image collection hardware.10. The computer-implemented method of claim 1, wherein: the useridentity information of the user comprises one or more of physiologicalcharacteristic information of the user, the user identity informationcollecting hardware comprises audio collection hardware in the billmanagement terminal, and the obtaining, by the bill management terminal,the user identity information of the user by using the user identityinformation collecting hardware comprises obtaining, by the billmanagement terminal, sound information of the user using the audiocollection hardware.
 11. The computer-implemented method of claim 1,wherein: the user identity information of the user comprises one or moreof physiological characteristic information of the user, the useridentity information collecting hardware comprises iris collectionhardware, and the obtaining, by the bill management terminal, the useridentity information of the user by using the user identity informationcollecting hardware comprises obtaining, by the bill managementterminal, iris information of the user using the iris collectionhardware.
 12. The computer-implemented method of claim 1, wherein: theuser identity information of the user comprises one or more ofphysiological characteristic information of the user, the user identityinformation collecting hardware comprises fingerprint collectionhardware deployed in the bill management terminal; and the obtaining, bythe bill management terminal, the user identity information of the userby using the user identity information collecting hardware comprisesobtaining, by the bill management terminal, fingerprint information ofthe user using the fingerprint collection hardware.
 13. Thecomputer-implemented method of claim 1, further comprising: obtaining,by the bill management terminal, a bill number of the paper bill; andsending, by the bill management terminal and to the network node on theblockchain, a sixth request comprising an association relationshipbetween the bill number of the paper bill and the identifier of thetarget electronic bill.
 14. The computer-implemented method of claim 13,further comprising: receiving, by the network node on the blockchain,the sixth request comprising the association relationship between thebill number of the paper bill and the identifier of the targetelectronic bill; and publishing, by the network node on the blockchain,the association relationship between the bill number of the paper billand the identifier of the target electronic bill on the blockchain. 15.A computer system, comprising: a network node on a blockchain; and abill management terminal coupled to the network node, wherein: thenetwork node on the blockchain stores a target electronic bill, whereinthe target electronic bill comprises an identifier of the targetelectronic bill and identity information of a payment user in the targetelectronic bill; the bill management terminal is configured to: receivea first input of a user, wherein the first input of the user comprises afirst request to associate the user with the target electronic bill andthe identifier of the target electronic bill; and send, to the networknode, a second request to associate the user with the target electronicbill stored in the blockchain, wherein the second request comprises theidentifier of the target electronic bill; the network node on theblockchain is configured to: receive the second request; in response toreceiving the second request, search for the target electronic bill inthe blockchain based on the identifier of the target electronic billcomprised in the second request; determine that the target electronicbill stored in the blockchain is not associated with user identityinformation of the user; and in response to determining that the targetelectronic bill stored in the blockchain is not associated with the useridentity information of the user, send, to the bill management terminal,a third request for user information; the bill management terminal isfurther configured to: in response to receiving the third request foruser information, collect the user identity information of the user fromuser identity information collecting hardware by: activating the useridentity information collecting hardware; and obtaining the useridentity information of the user by using the user identity informationcollecting hardware; and send, to the network node on the blockchain,the user identity information of the user; the network node on theblockchain is further configured to: receive, from the bill managementterminal, the user identity information of the user; verify whether theuser identity information of the user matches the identity informationof the payment user in the target electronic bill; determine that theuser identity information of the user matches the identity informationof the payment user in the target electronic bill; and in response todetermining that the user identity information of the user matches theidentity information of the payment user in the target electronic bill,publish the matched determination on the blockchain; and the billmanagement terminal is further configured to: receive a second input ofthe user, the second input of the user comprising a print operation toprint the target electronic bill; activate print hardware coupled withthe bill management terminal; and print a paper bill corresponding tothe target electronic bill using the print hardware.
 16. The computersystem of claim 15, wherein the bill management terminal is furtherconfigured to: obtain a bill number of the paper bill; and send, to thenetwork node on the blockchain, a sixth request comprising anassociation relationship between the bill number of the paper bill andthe identifier of the target electronic bill.
 17. The computer system ofclaim 16, wherein the network node is further configured to: receive thesixth request comprising the association relationship between the billnumber of the paper bill and the identifier of the target electronicbill; and publish the association relationship between the bill numberof the paper bill and the identifier of the target electronic bill onthe blockchain.
 18. The computer system of claim 15, wherein the useridentity information of the user is collected by the bill managementterminal, in response to displaying a prompt for the user identityinformation.
 19. The computer system of claim 15, wherein: the useridentity information of the user comprises an identity card number ofthe user, and the user identity information collecting hardwarecomprises identity card scanning hardware, and the obtaining the useridentity information of the user by using the user identity informationcollecting hardware comprises obtaining the identity card number of theuser by scanning an identity card of the user using the identity cardscanning hardware.
 20. The computer system of claim 15, wherein: theuser identity information of the user comprises one or more ofphysiological characteristic information of the user, the user identityinformation collecting hardware comprises image collection hardware, andthe obtaining the user identity information of the user by using theuser identity information collecting hardware comprises obtaining a faceimage of the user using the image collection hardware.